Skip to content

Add FAQ entry for JabRef not starting on Wayland#619

Merged
koppor merged 5 commits intoJabRef:mainfrom
viictor1:doc-update-for-issue-11489
Mar 24, 2026
Merged

Add FAQ entry for JabRef not starting on Wayland#619
koppor merged 5 commits intoJabRef:mainfrom
viictor1:doc-update-for-issue-11489

Conversation

@viictor1
Copy link
Copy Markdown
Contributor

This PR adds a FAQ entry to linux.md documenting that JabRef requires XWayland to run on Wayland-based systems, as discussed in JabRef/jabref#11489.

Copy link
Copy Markdown
Member

@koppor koppor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please learn about heading levels and structuring of documents...

I don't tell the solution to educate

@koppor
Copy link
Copy Markdown
Member

koppor commented Mar 18, 2026

Moreover link to debian package

@viictor1
Copy link
Copy Markdown
Contributor Author

Thanks for the feedback! I believe it's fixed now.

@viictor1 viictor1 requested a review from koppor March 18, 2026 11:29
@viictor1 viictor1 force-pushed the doc-update-for-issue-11489 branch from 7db9008 to e714c53 Compare March 18, 2026 14:17
@viictor1 viictor1 requested a review from koppor March 18, 2026 14:18
@viictor1
Copy link
Copy Markdown
Contributor Author

Hello, could you review this again please? I put the best link I could find but if you still don't like it just let me know.

Co-authored-by: ThiloteE <73715071+ThiloteE@users.noreply.github.com>
@viictor1 viictor1 requested a review from ThiloteE March 24, 2026 17:15
@koppor koppor merged commit b4610ee into JabRef:main Mar 24, 2026
3 checks passed
@koppor
Copy link
Copy Markdown
Member

koppor commented Mar 24, 2026

I fixed the position, heading level, and the package name casing.

Merged since it is important to share the knowledge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants